Web conference replay association upon meeting completion

ABSTRACT

A method, computer system, and computer program product for web conference replay association are provided. The embodiment may include recording a web meeting utilizing web conference software. The embodiment may also include parsing meeting invitation information associated with the recorded web meeting. The embodiment may further include extracting meeting-related information associated with the recorded meeting. The embodiment may also include updating meeting replay information based on the extracted meeting-related information by modifying an original meeting invitation. The embodiment may further include sending an update notification to a required participant.

BACKGROUND

The present invention relates, generally, to the field of computing, and more particularly to web conferencing systems.

Web conferencing systems allow users to hold live meetings, training events, lectures or presentations through a web conferencing system on TCP/IP connections. Web conferencing systems also allow data streams of text-based messages and voice and video chat to be shared simultaneously. Users can connect to the web conferencing system by telephone or using a user computer's speakers and microphone through a VoIP connection. Often, web conferences are recorded on the user side or server side for later viewing or distribution using a software or a web-based application. Recordings may be saved in the cloud or on a user computer. For example, if a user uses cloud recording, the recording will be automatically saved online and related information may be accessed on the user's meeting history page.

SUMMARY

According to one embodiment, a method, computer system, and computer program product for web conference replay association are provided. The embodiment may include recording a web meeting utilizing web conference software. The embodiment may also include parsing meeting invitation information associated with the recorded web meeting. The embodiment may further include extracting meeting-related information associated with the recorded meeting. The embodiment may also include updating meeting replay information based on the extracted meeting-related information by modifying an original meeting invitation. The embodiment may further include sending an update notification to a required participant.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

These and other objects, features, and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings. The various features of the drawings are not to scale as the illustrations are for clarity in facilitating one skilled in the art in understanding the invention in conjunction with the detailed description. In the drawings:

FIG. 1 illustrates an exemplary networked computer environment according to at least one embodiment;

FIG. 2 is an operational flowchart illustrating a web conference replay association process according to at least one embodiment;

FIG. 3 is an exemplary diagram depicting an updated calendar entry with meeting replay information according to at least one embodiment:

FIG. 4 is an exemplary diagram depicting a web conferencing tool overlaid with web conference recording information utilizing a web conference replay association process according to at least one embodiment;

FIG. 5 is a block diagram of internal and external components of computers and servers depicted in FIG. 1 according to at least one embodiment;

FIG. 6 depicts a cloud computing environment according to an embodiment of the present invention; and

FIG. 7 depicts abstraction model layers according to an embodiment of the present invention.

DETAILED DESCRIPTION

Detailed embodiments of the claimed structures and methods are disclosed herein; however, it can be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods that may be embodied in various forms. This invention may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.

Embodiments of the present invention relate to the field of computing, and more particularly to web conferencing systems. The following described exemplary embodiments provide a system, method, and program product to extract critical information from a web conference recording and update the recording with available replay information when distributing the recording with such replay information. Therefore, the present embodiment has the capacity to improve the technical field of web conferencing systems by evaluating meeting information and creating recording markers or replay information that are specific to a meeting and prompting the meeting details to a user, thereby allowing a meeting host to timely share the meeting recording without manually updating, modifying or sending the meeting recording.

As previously described, web conferencing systems allow users to hold live meetings, training events, lectures or presentations through a web conferencing system on TCP/IP connections. Web conferencing systems also allow data streams of text-based messages and voice and video chat to be shared simultaneously. Users can connect to the web conferencing system by telephone or using a user computer's speakers and microphone through a VoIP connection. Often, web conferences are recorded on the user side or server side for later viewing or distribution using a software or a web-based application. Recordings may be saved in the cloud or on a user computer. For example, if a user uses cloud recording, the recording will be automatically saved online and related information may be accessed on the user's meeting history page.

Web conferencing systems may be seen as a convenient way to hold a meeting via the internet and share meeting content with multiple groups. However, problems may arise when an individual needs to attend different meetings within a short time frame or needs to multitask during meetings. In such situations, the meeting host usually receives an email with meeting replay information. The meeting host then needs to decide when and with whom the meeting host needs to share the replay link and password. It may also be difficult to keep track of all the meeting information. As such, it may be advantageous to, among other things, implement a system capable of extracting important information from the meeting recording and associating the important information with the replay information, such that the replay information may be timely sent to the individuals who did not attend the meeting without taking up the meeting host's time and efforts.

According to one embodiment, the present invention may extract important meeting-related information from meeting recordings. In at least one other embodiment, the present invention may also automatically update or modify replay information, such that a recipient of the replay information may recall topics or the purpose of a particular meeting more easily even before replaying the recorded meeting by checking the updated or modified information first. The present invention may further automatically send a notification with updated meeting-related information to a meeting participant. Such meeting-related information may include meeting name, meeting length, meeting date, meeting time, URL of recording, meeting participants, meeting participants responses, meeting topic and password to access the recording.

The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include the computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or another device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The following described exemplary embodiments provide a system, method, and program product for automatically updating recorded web meeting with important meeting-related information and sending an update notification to a meeting participant.

Referring to FIG. 1, an exemplary networked computer environment 100 is depicted according to at least one embodiment. The networked computer environment 100 may include client computing device 102 and a server 112 interconnected via a communication network 114. According to at least one implementation, the networked computer environment 100 may include a plurality of client computing devices 102 and servers 112 of which only one of each is shown for illustrative brevity.

The communication network 114 may include various types of communication networks, such as a wide area network (WAN), local area network (LAN), a telecommunication network, a wireless network, a public switched network and/or a satellite network. The communication network 114 may include connections, such as wire, wireless communication links, or fiber optic cables. It may be appreciated that FIG. 1 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

Client computing device 102 may include a processor 104 and a data storage device 106 that is enabled to host and run a software program 108 and a web conference replay association program 110A and communicate with the server 112 via the communication network 114, in accordance with one embodiment of the invention. Client computing device 102 may be, for example, a mobile device, a telephone, a personal digital assistant, a netbook, a laptop computer, a tablet computer, a desktop computer, or any type of computing device capable of running a program and accessing a network. As will be discussed with reference to FIG. 5, the client computing device 102 may include internal components 502 a and external components 504 a, respectively.

The server computer 112 may be a laptop computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device or any network of programmable electronic devices capable of hosting and running a web conference replay association program 110B and a database 116 and communicating with the client computing device 102 via the communication network 114, in accordance with embodiments of the invention. As will be discussed with reference to FIG. 5, the server computer 112 may include internal components 502 b and external components 504 b, respectively. The server 112 may also operate in a cloud computing service model, such as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS). The server 112 may also be located in a cloud computing deployment model, such as a private cloud, community cloud, public cloud, or hybrid cloud.

According to the present embodiment, the web conference replay association program 110A, 110B may be a program capable of extracting key information from a user email or calendar associated with a recorded web meeting and updating or modifying replay information of the recorded web meeting. The web conference replay association process is explained in further detail below with respect to FIG. 2.

Referring to FIG. 2, an operational flowchart illustrating a web conference replay association process 200 is depicted according to at least one embodiment. At 202, the web conference replay association program 110A, 110B records a web meeting. According to one embodiment, the intelligent web meeting bookmarking program 110A, 110B may record a web meeting in either audio or video format depending on a user selection. In at least one other embodiment, the intelligent web meeting bookmarking program 110A, 110B may ingest documents shared during a web meeting, such as word processing or text documents, spreadsheets, presentations, images, PDFs, videos, or maps and attach said files to the recording.

At 204, the web conference replay association program 110A, 110B parses emails or calendar information associated with the recorded web meeting. According to one embodiment, the web conference replay association program 110A, 110B may monitor for the receipt of the meeting recording details. For example, a user may receive an email with a notification stating that the meeting recording is available for viewing. In the alternative, a user may receive notification of an updating of the available recording on a web conferencing system. The web conference replay association program 110A, 110B may also access and monitor a user's calendar application or online calendar to pinpoint a specific meeting taking place and check the date and the time when the meeting is scheduled for. The web conference replay association program 110A, 110B may further parse other meeting invitation information received from chat applications or instant messaging programs.

At 206, the web conference replay association program 110A, 110B extracts key information from the recorded meeting. According to one embodiment, the web conference replay association program 110A, 110B may extract information, such as, names of participants, length of a meeting, date and time when the meeting was held, URL or password required when joining a web meeting, etc. The web conference replay association program 110A, 110B may also extract certain important information from user emails or calendar entries associated with the recorded meeting. For example, if a user A is invited to attend a meeting related to project A and the user A email invite or calendar invite contains a title “project A meeting”, the web conference replay association program 110A, 110B may extract such title to update the replay information in later steps. In at least one other embodiment, the web conference replay association program 110A, 110B may utilize a known voice recognition technique to extract the same key information from the recording when such information is not available at the outset.

At 208, the web conference replay association program 110A, 110B updates available replay information. According to one embodiment, the web conference replay association program 110A, 110B may perform updates with the extracted information in step 206, such that the original meeting invitation may be modified to include the recording details (e.g. title, date, time, length and participants, etc.) The modified information may be viewable on the summary view of the meeting or within the meeting details upon opening the meeting. In at least one other embodiment, the web conference replay association program 110A, 110B may send a calendar update notification to attendees. In the alternative, a host of a web meeting may elect to send the calendar updates with the replay information only to those attendees who did not listen live. Such updated information may automatically be sent via email to participants who were originally indicated as required participants. For optional meeting attendees, the web conference replay association program 110A, 110B may send replay information with additional details or meeting materials.

The web conference replay association program 110A, 110B may also determine which web conference recording is associated with which email when multiple emails are found related to a web conference. For example, a 30 minute meeting is likely associated with a 30 minute-long recording, whereas 60 minute meeting may be associated with a 58 minute-long recording. Further, a meeting that ended at noon may be likely associated with an email that was sent at 12:30 p.m., not emails about a web conference recording that was received at 11:45 a.m. or 1:30 p.m. In at least one other embodiment, the web conference replay association program 110A, 110B may also determine who is hosting a web conference and disregard emails or forwarded notes that are not addressed to the correct moderator or host of the web meeting. For example, if a user receives a recording email at 12:00 p.m. and the user's meeting ended at 12:05 p.m., the web conference replay association program 110A, 110B may determine that the recording email is not for the meeting in which the user just participated.

Referring now to FIG. 3, an exemplary diagram depicting an updated calendar entry with meeting replay information is depicted according to at least one embodiment. According to one embodiment, the web conference replay association program 110A, 110B may update a user calendar entry 302 that may include a title or agenda of the meeting information 304, “Business Operations Review—App Factory IoT4 Buildings” and may also include the information related to a host of a web meeting 304 with additional information related to the web conference replay after the web conference recording has completed 308, 310 and 312. For example, the web conference replay association program 110A, 110B may modify the calendar entry 302 associated with the web conference replay after the recording is completed, with the link to the replay 308, the password for the replay 310, and the length of the replay 312.

Referring now to FIG. 4, an exemplary diagram depicting a web conferencing tool overlaid with web conference recording information utilizing a web conference replay association process is depicted according to at least one embodiment. According to one embodiment, the web conference replay association program 110A, 110B may parse original summary information 402 that contains links to various meeting recordings, 404, 406, 408, 410 and 412. The web conference replay association program 110A, 110B may then parse recordings and related emails or calendar information to extract key information to update the summary replay information 404, 406, 408, 410 and 412. Diagram 414 represents an exemplary summary page of a web conference tool after the web conference replay association program 110A, 110B updates replay information. For example, the web conference replay association program 110A, 110B may update entry 404 and replace the information with more detailed information 416. User A's WebEx replay information 406 may now be updated to read “IoT Building Insights Partner Conference” 418. In at least one other embodiment, a confidence score on the associated meeting may be shown. For example, the web conference replay association program 110A, 110B may determine that it is 98% confident that the meeting corresponds to the 2 p.m.-3 p.m. calendar entry for “IoT Building Insights Partner Conference” on October 2018. The web conference replay association program 110A, 110B may determine a confidence score based on the timing of when the replay available email comes into an email inbox of a moderator or a host of the meeting and the completion of the meeting. The web conference replay association program 110A, 110B may further update the entries 408 and 410 and the entry 420 and 422 may indicate “sales call” and “1:1 meeting between Bob and Mary” accordingly.

It may be appreciated that FIGS. 2-4 provide only an illustration of one implementation and do not imply any limitations with regard to how different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements. For example, in at least one embodiment, the web conference replay association program 110A, 110B may share a replay link, password and other details within a web service for any other subscribers who were not originally invited to the meeting. The web conference replay association program 110A, 110B may also ask the host of a meeting how or if the host wants to share the replay information.

FIG. 5 is a block diagram of internal and external components of the client computing device 102 and the server 112 depicted in FIG. 1 in accordance with an embodiment of the present invention. It should be appreciated that FIG. 5 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

The data processing system 502, 504 is representative of any electronic device capable of executing machine-readable program instructions. The data processing system 502, 504 may be representative of a smartphone, a computer system, PDA, or other electronic devices. Examples of computing systems, environments, and/or configurations that may represented by the data processing system 502, 504 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputer systems, and distributed cloud computing environments that include any of the above systems or devices.

The client computing device 102 and the server 112 may include respective sets of internal components 502 a,b and external components 504 a,b illustrated in FIG. 5. Each of the sets of internal components 502 include one or more processors 520, one or more computer-readable RAMs 522, and one or more computer-readable ROMs 524 on one or more buses 526, and one or more operating systems 528 and one or more computer-readable tangible storage devices 530. The one or more operating systems 528, the software program 108 and the web conference replay association program 110A in the client computing device 102 and the web conference replay association program 110B in the server 112 are stored on one or more of the respective computer-readable tangible storage devices 530 for execution by one or more of the respective processors 520 via one or more of the respective RAMs 522 (which typically include cache memory). In the embodiment illustrated in FIG. 5, each of the computer-readable tangible storage devices 530 is a magnetic disk storage device of an internal hard drive. Alternatively, each of the computer-readable tangible storage devices 530 is a semiconductor storage device such as ROM 524, EPROM, flash memory or any other computer-readable tangible storage device that can store a computer program and digital information.

Each set of internal components 502 a,b also includes an R/W drive or interface 532 to read from and write to one or more portable computer-readable tangible storage devices 538 such as a CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk or semiconductor storage device. A software program, such as a web conference replay association program 110A, 110B can be stored on one or more of the respective portable computer-readable tangible storage devices 538, read via the respective R/W drive or interface 532 and loaded into the respective hard drive 530.

Each set of internal components 502 a,b also includes network adapters or interfaces 536 such as a TCP/IP adapter cards, wireless Wi-Fi interface cards, or 3G or 4G wireless interface cards or other wired or wireless communication links. The software program 108 and the web conference replay association program 110A in the client computing device 102 and the web conference replay association program 110B in the server 112 can be downloaded to the client computing device 102 and the server 112 from an external computer via a network (for example, the Internet, a local area network or other, wide area network) and respective network adapters or interfaces 536. From the network adapters or interfaces 536, the software program 108 and the web conference replay association program 110A in the client computing device 102 and the web conference replay association program 110B in the server 112 are loaded into the respective hard drive 530. The network may comprise copper wires, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.

Each of the sets of external components 504 a,b can include a computer display monitor 544, a keyboard 542, and a computer mouse 534. External components 504 a,b can also include touch screens, virtual keyboards, touch pads, pointing devices, and other human interface devices. Each of the sets of internal components 502 a,b also includes device drivers 540 to interface to computer display monitor 544, keyboard 542, and computer mouse 534. The device drivers 540, R/W drive or interface 532, and network adapter or interface 536 comprise hardware and software (stored in storage device 530 and/or ROM 524).

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein is not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is a service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring now to FIG. 6, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 100 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 100 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 6 are intended to be illustrative only and that computing nodes 100 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 7, a set of functional abstraction layers 700 provided by cloud computing environment 50 is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 7 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and web conference replay association 96. Web conference replay association 96 may relate to updating a calendar entry with meeting related information extracted from the related emails or original calendar entries.

The descriptions of the various embodiments of the present invention have been presented for purposes of illustration but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. 

What is claimed is:
 1. A processor-implemented method for web conference replay association, the method comprising: recording a web meeting utilizing a web conference software; parsing meeting invitation information associated with the recorded web meeting; extracting meeting-related information associated with the recorded meeting; updating meeting replay information based on the extracted meeting-related information by modifying an original meeting invitation; and sending an update notification to a required participant.
 2. The method of claim 1, wherein the extracted meeting-related information is selected from a group consisting of meeting name, meeting length, meeting date, meeting time, URL of recording, meeting participants, meeting participants responses, meeting topic and password to access the recording.
 3. The method of claim 1, further comprising: updating a calendar entry related to the recorded web meeting based on the extracted meeting-related information.
 4. The method of claim 1, further comprising: updating a summary view generated by the web conference software based on the extracted meeting-related information.
 5. The method of claim 1, further comprising: determining potential listeners who were unable to attend the web meeting based on meeting data; and providing the determined potential listeners with the meeting replay information, wherein the meeting replay information includes a replay link and a password.
 6. The method of claim 1, further comprising: determining a correct email that is associated with the meeting replay information based on a time length of the web meeting and a timestamp of the determined correct email. The method of claim 1, further comprising: determining additional emails or forwarded notes that are not addressed to a correct meeting host based on a comparison of a timestamp of each determined email or each forwarded note and an ending time of the web meeting.
 8. A computer system for web conference replay association, the computer system comprising: one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage media, and program instructions stored on at least one of the one or more tangible storage media for execution by at least one of the one or more processors via at least one of the one or more memories, wherein the computer system is capable of performing a method comprising: recording a web meeting utilizing a web conference software; parsing meeting invitation information associated with the recorded web meeting; extracting meeting-related information associated with the recorded meeting; updating meeting replay information based on the extracted meeting-related information by modifying an original meeting invitation; and sending an update notification to a required participant.
 9. The computer system of claim 8, wherein the extracted information is selected from a group consisting of meeting name, meeting length, meeting date, meeting time, URL of recording, meeting participants, meeting participants responses, meeting topic and password to access the recording.
 10. The computer system of claim 8, further comprising: updating a calendar entry related to the recorded web meeting based on the extracted meeting-related information.
 11. The computer system of claim 8, further comprising: updating a summary view generated by the web conference software based on the extracted meeting-related information.
 12. The computer system of claim 8, further comprising: determining potential listeners who were unable to attend the meeting based on the meeting data; and providing the determined potential listeners with the meeting replay information, wherein the meeting replay information includes a replay link and a password.
 13. The computer system of claim 8, further comprising: determining a correct email that is associated with the meeting replay information based on a time length of the web meeting and a timestamp of the determined correct email.
 14. The computer system of claim 8, further comprising: determining additional emails or forwarded notes that are not addressed to a correct meeting host based on a comparison of a timestamp of each determined email or each forwarded note and an ending time of the web meeting.
 15. A computer program product for web conference replay association, the computer program product comprising: one or more computer-readable tangible storage media and program instructions stored on at least one of the one or more tangible storage media, the program instructions executable by a processor of a computer to perform a method, the method comprising: recording a web meeting utilizing a web conference software; parsing meeting invitation information associated with the recorded web meeting; extracting meeting-related information associated with the recorded meeting; updating meeting replay information based on the extracted meeting-related information by modifying an original meeting invitation; and sending an update notification to a required participant.
 16. The computer program product of claim 15, wherein the extracted information is selected from a group consisting of meeting name, meeting length, meeting date, meeting time, URL of recording, meeting participants, meeting participants responses, meeting topic and password to access the recording.
 17. The computer program product of claim 15, further comprising: updating a calendar entry related to the recorded web meeting based on the extracted meeting-related information.
 18. The computer program product of claim 15, further comprising: updating a summary view generated by the web conference software based on the extracted meeting-related information.
 19. The computer program product of claim 15, further comprising: determining potential listeners who were unable to attend the meeting based on the meeting data; and providing the determined potential listeners with the meeting replay information, wherein the meeting replay information includes a replay link and a password.
 20. The computer program product of claim 15, further comprising: determining a correct email that is associated with the meeting replay information based on a time length of the web meeting and a timestamp of the determined correct email. 